Search Results

Maximum Brake Torque (MBT) timing for an internal combustion engine is the minimum advance of spark timing for best torque. Traditionally, MBT timing is an open loop feedforward control whose values are experimentally determined by conducting spark sweeps at different speed, load points and at different environmental operating conditions. Almost every calibration point needs a spark sweep to see if the engine can be operated at the MBT timing condition. If not, a certain degree of safety margin is needed to avoid pre-ignition or knock during engine operation. Open-loop spark mapping usually requires a tremendous amount of effort and time to achieve a satisfactory calibration. This paper shows that MBT timing can be achieved by regulating a composite feedback measure derived from the in-cylinder ionization signal referenced to a top dead center crank angle position. A PI (proportional and integral) controller is used to illustrate closed-loop control of MBT timing.

One challenge facing automotive product development teams is the inclusion of the Human System Integration (HSI) community – consisting of human factors professionals, graphic and industrial designers, rapid prototyping software engineers, electronic hardware engineers, and systems engineers – in the Product Development Process (PDP). In order to achieve this integration, Visteon looked to the methods of systems engineering currently employed throughout the PDP. Overlaying the HSI process with an accepted systems engineering process description known as the N2 (N-squared) chart resulted in the outlining of expected inputs to the HSI process team, definitions of processes undertaken by the team, and expected outputs of those processes.

Spark timing of an Internal Combustion (IC) engine is often limited by engine knock in the advanced direction. The ability to operate the engine at its advanced (borderline knock) spark limit is the key for improving output power and fuel economy. Due to combustion cycle-to-cycle variations, IC engine combustion behaves similar to a random process and so does the engine performance criteria, such as IMEP (Indicated Mean Effective Pressure), and knock intensity. The combustion stability measure COVariance of IMEP assumes the IMEP is a random process. Presently, the spark limit control of IC engines is deterministic in nature. The controller does not utilize any stochastic information associated with control parameters such as knock intensity for borderline spark limit control. This paper proposes a stochastic limit control strategy for borderline knock control. It also develops a simple stochastic model for evaluating the proposed stochastic controller.

Data design is a very critical step in the model-based software development process. This paper discusses the importance of a data dictionary in modeling, automatic code generation and in creating model dependency graphs.

Software is today one of the most important components of electronic products. The capture and validation of the requirements makes a difference if the product will fulfill the customer's expectations or generate enormous frustration. The correct implementation of software validation makes the Product Development Organization more mature and reliable. Software validation is an opportunity for the product development team to identify if the requirements and customer expectations were achieved. It is also used to identify the risks and possible improvements to the product. Software testing is one element of a brooder topic that is often referred to as verification and validation (V&V). Verification refers to the set of activities that ensure that software correctly implements a specific function. Validation refers to a different set of activities that ensure that the software that has been built is traceable to customer requirements.

The automotive aftermarket represents a challenge for supply chain management when compared to traditional practices in the original equipment manufacturer (OEM) supply chain. This paper presents a case study for a Tier One automotive supplier’s challenges with inventory carrying costs, backorder risk, and supplier relationships for a rear seat entertainment system in the automotive aftermarket. It will also address the lean principles used to improve the business and increase material planning analyst productivity. A call for OEMs to examine their business practices is also included.

High-power LEDs and LED headlamps have become a serious consideration for the automotive industry. White LEDs have achieved the required performance for initial automotive headlamp applications. However tradeoffs among several attributes such as efficiency, cost, weight and performance profoundly affect LED headlamp development and need to be addressed by vehicle manufacturers, lamp set makers and LED source suppliers in order for LED headlamps to be effective. The solutions to these tradeoffs relates to the behavior of the LED sources, the thermo-mechanical integration of LEDs in a headlamp environment and input from the vehicle manufacturer regarding styling and packaging for an LED headlamp on the respective targeted vehicles.

A test load specification is required to validate an automotive product to meet the durability and design life requirements. Traditionally in the automotive industry, load specifications for design validation tests are directly given by OEMs, which are generally developed from an envelop of generic customer usage profiles and are, in most cases, over-specified. In recent years, however, there are many occasions that a proposed load specification for a particular product is requested. The particular test load specification for a particular product is generated based on the measured load data at its mounting location on the given type of vehicles, which contains more realistic time domain load levels and associated frequency contents. The measured time domain load is then processed to frequency domain test load data by using the fast Fourier transform and damage equivalent techniques.

Today open source software is widely used in different domains like Desktop systems, Consumer electronics (smart phones, TV, washing machines, camera, printers, smart watches), Automotive, Automation etc. With the increased involvement of the open source software in the different domains including the safety critical ones, there has been a requirement of the well-defined test strategy to test and verify such systems. Currently there are multiple open source tools and frameworks to choose from. The paper describes the various open source test strategies and tools available to qualify such systems, their features, maintenance, community support, advantages and disadvantages. Target audience would be the software engineers, program managers, using an open source stack for the product development.

To obtain the maximum output power and fuel economy from an internal combustion engine, it is often necessary to detect engine knock and operate the engine at its knock limit. This paper presents the ability to detect knock using in-cylinder ionization signals on a large displacement, air-cooled, “V” twin motorcycle engine over the engine operational map. The knock detection ability of three different sensors is compared: production knock (accelerometer) sensor, in-cylinder pressure sensor, and ionization sensor. The test data shows that the ionization sensor is able to detect knock better than the production knock sensor when there is high mechanical noise present in the engine.